OPC Studio User's Guide and Reference
Administer OPC UA Application Dialog
Client and Subscriber Development > Features > User Interface > Administer OPC UA Application Dialog

For an OPC UA application to coexist and communicate properly in the operating system and in the OPC UA ecosystem, it needs to fulfill certain conditions, and integrate in the prescribed way with the environment. From the code, this what the OPC UA Application object offers. There are aspects of most OPC UA applications that need to be administered by the end user. In Windows desktop application, QuickOPC offers a ready-made dialog for this, and you can integrate this dialog into your application.

The "Administer OPC UA Application" dialog allows:

The dialog can be integrated into your application in following ways:

With any of the above methods, you can specify whether the end user will be allowed to change the password to the private key of the own application certificate. Changing the private key password should be disallowed if your application logic maintains the password itself, or if you have not implemented the logic to persist the private key password (if the user was allowed to change the private but your application won't persist it, the passowrd will be incorrect next time the application is run, and it will not work).

For the end-user documentation, i.e. how the user of your application can operate the dialog, see Dialog: Administer OPC UA Application.

In this version, the operation on the OPC UA application are always scoped to the currently running executable. In some environments, the same top-level executable might be used for multiple logical programs. This typically happens with interpreted languages, such VBScript or Python. Keep in mind that OPC UA requires that each OPC UA application is uniquely identified. In this case, however, if the interpreter is used to run different programs, they will all look like a single OPC UA application.
See Also

Reference

Knowledge Base